Low power network connectivity of a building control device

ABSTRACT

A device incorporating electronics including a transmitter to transmit commands to a remote HVAC unit, a communication module for connecting the device to a low power network, and a controller to communicate with the HVAC unit and communicate with a remote device over the low power network. The device further incorporates a power source to power the electronics.

TECHNICAL FIELD

The disclosure relates generally to building automation systems, andmore particularly to building control devices for use in such buildingautomation systems.

BACKGROUND

Low power networks such as low power wireless networks (LPWANs) werecreated for machine-to-machine (M2M) and Internet of things (IoT)networks. LPWANs operate at a lower cost with greater power efficiencythan traditional mobile networks. They are also able to support agreater number of connected devices over a larger area. LPWANs canaccommodate packet sizes from 10 to 1,000 bytes at uplink speeds up to200 Kbps. LPWAN's long range varies from 2 km to 1,000 km, depending onthe technology. Furthermore, LPWAN is not a single technology, but agroup of various low-power, wide area network technologies that takemany shapes and forms. LPWANs can use licensed or unlicensed frequenciesand include proprietary or open standard options. Some LPWANs may runover a public network in the 868 MHz or 902 MHz bands. These LPWANs candeliver messages over distances of 30-50 km in rural areas, 3-10 km inurban settings and up to 1,000 km in line-of-site applications. Randomphase multiple access (RPMA) is another type of LPWAN. Though it has ashorter range (up to 50 km line of sight and with 5-10 km non-line ofsight), it offers better bidirectional communication.

SUMMARY

In an example of the disclosure, a device may incorporate electronicsincluding a transmitter configured to wirelessly transmit one or morecommands to a remote HVAC unit, a communication module for connectingthe device to a low power network, and a controller. The controller maybe configured to communicate with the HVAC unit via the transmitter, andcommunicate with a remote device over the low power network via thecommunication module. The device may also include a power sourceoperatively coupled to the electronics and configured to power theelectronics.

Alternatively or additionally to the foregoing, the device may befurther configured to communicate via the transmitter with one or moresensors for sensing environmental conditions.

Alternatively or additionally to any of the embodiments above, theelectronics may further incorporate one or more sensors for sensingenvironmental conditions.

Alternatively or additionally to any of the embodiments above, thedevice may further incorporate a housing with the electronics and powersource disposed therein.

Alternatively or additionally to any of the embodiments above, theelectronics may further incorporate a user interface including adisplay, wherein the controller is configured to display on the displaycurrent environmental conditions and desired environmental conditionsspecified by a user via the user interface.

Alternatively or additionally to any of the embodiments above, theremote device may send instructions over the low power network to thedevice to control the HVAC unit.

Alternatively or additionally to any of the embodiments above, the lowpower network may be a low power wide area network (LPWAN).

Alternatively or additionally to any of the embodiments above, the LPWANmay be a NarrowB and Internet of Things (NB-IoT) Network.

Alternatively or additionally to any of the embodiments above, the LPWANmay be a LoRa Network.

Alternatively or additionally to any of the embodiments above, thedevice may be a thermostat.

In another example of the disclosure, a thermostat may incorporate atransmitter configured to wirelessly transmit one or more commands to aremote HVAC unit, a communication module for connecting the device to alow power network, and a controller operatively connected to thetransmitter and the communication module. The controller may beconfigured to communicate with the HVAC unit via the transmitter, andcommunicate with a remote device over the low power network via thecommunication module. The thermostat may also include a power sourceoperatively coupled to the transmitter, the communication module, andthe controller and configured to power the transmitter, thecommunication module, and the controller.

Alternatively or additionally to the foregoing, the thermostat mayfurther incorporate a housing with the transmitter, the communicationmodule, the controller, and the power source disposed therein.

Alternatively or additionally to any of the embodiments above, thethermostat may further incorporate one or more sensors for sensingenvironmental conditions, and a user interface including a display,wherein the controller may be configured to display on the display theenvironmental conditions and desired environmental conditions specifiedby a user via the user interface.

Alternatively or additionally to any of the embodiments above, thethermostat may be further configured to communicate via the transmitterwith one or more sensors for sensing environmental conditions and thethermostat may further incorporate a user interface including a display,wherein the controller is configured to display on the display theenvironmental conditions and desired environmental conditions specifiedby a user via the user interface.

Alternatively or additionally to any of the embodiments above, the lowpower network may be a NarrowB and Internet of Things (IoT) Network.

Alternatively or additionally to any of the embodiments above, the lowpower network may be a LoRa Network.

In another example of the disclosure, a thermostat may incorporate ahousing and electronics disposed within the housing. The electronics mayinclude a transmitter configured to wirelessly transmit one or morecommands to a remote HVAC unit, a communication module for connectingthe device to a low power wide area network (LPWAN), and a controller.The controller may be configured to communicate with the HVAC unit viathe transmitter and communicate with a remote device over the LPWAN viathe communication module. The electronics may further include a userinterface including a display, wherein the controller is configured todisplay on the display environmental conditions and desiredenvironmental conditions specified by a user via the user interface. Thethermostat may also incorporate a power source disposed within thehousing, operatively coupled to the electronics, and configured to powerthe electronics.

Alternatively or additionally to the foregoing, the electronics mayfurther incorporate one or more sensors for sensing environmentalconditions.

Alternatively or additionally to any of the embodiments above, thecontroller may be further configured to communicate via the transmitterwith one or more sensors for sensing environmental conditions.

Alternatively or additionally to any of the embodiments above, the LPWANmay be a NarrowB and Internet of Things (IoT) Network.

The above summary of some illustrative embodiments is not intended todescribe each disclosed embodiment or every implementation of thepresent disclosure. The Figures and Description which follow moreparticularly exemplify these and other illustrative embodiments.

BRIEF DESCRIPTION OF THE FIGURES

The disclosure may be more completely understood in consideration of thefollowing description in connection with the accompanying drawings, inwhich:

FIG. 1 is a schematic block diagram of an illustrative building controldevice;

FIG. 2 is a schematic view of an illustrative building control device;

FIGS. 3A-3C are schematic views illustrating an approach for connectinga mobile device to a building control device;

While the disclosure is amenable to various modifications andalternative forms, specifics thereof have been shown by way of examplein the drawings and will be described in detail. It should beunderstood, however, that the intention is not to limit the disclosureto the particular embodiments described. On the contrary, the intentionis to cover all modifications, equivalents, and alternatives fallingwithin the spirit and scope of the disclosure.

DESCRIPTION

For the following defined terms, these definitions shall be applied,unless a different definition is given in the claims or elsewhere inthis specification.

All numeric values are herein assumed to be modified by the term“about,” whether or not explicitly indicated. The term “about” generallyrefers to a range of numbers that one of skill in the art would considerequivalent to the recited value (i.e., having the same function orresult). In many instances, the terms “about” may include numbers thatare rounded to the nearest significant figure.

The recitation of numerical ranges by endpoints includes all numberswithin that range (e.g. 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and5).

As used in this specification and the appended claims, the singularforms “a”, “an”, and “the” include plural referents unless the contentclearly dictates otherwise. As used in this specification and theappended claims, the term “or” is generally employed in its senseincluding “and/or” unless the content clearly dictates otherwise.

It is noted that references in the specification to “an embodiment”,“some embodiments”, “other embodiments”, and so forth, indicate that theembodiment described may include one or more particular features,structures, and/or characteristics. However, such recitations do notnecessarily mean that all embodiments include the particular features,structures, and/or characteristics. Additionally, when particularfeatures, structures, and/or characteristics are described in connectionwith one embodiment, it should be understood that such features,structures, and/or characteristics may also be used connection withother embodiments whether or not explicitly described unless clearlystated to the contrary.

The following description should be read with reference to the drawingsin which similar structures in different drawings are numbered the same.The drawings, which are not necessarily to scale, depict illustrativeembodiments and are not intended to limit the scope of the disclosure.Although examples of construction, dimensions, and materials may beillustrated for the various elements, those skilled in the art willrecognize that many of the examples provided have suitable alternativesthat may be utilized.

A major issue in the connected product market, for example, theconnected thermostat market, is a requirement to provide a combinationof a long-term product life, while providing constant connectivity to acloud and/or local mobile device. Currently, there is a struggle toachieve a multi-year, full-power delivery, from a power source, such asbatteries or a so-called “power-stealing”, for example, while removing aburden of the user to replace the power source too often. Therefore, theissue is to deliver a device, such as a thermostat, which could run froma low-energy source (e.g., batteries, “power-stealing”, and the like),while being able to run from these sources as long as possible (e.g., 1year, 2 years, 3 years, 4 years, 5 years, and so on), while constantlymaintaining cloud connectivity. It is believed that the ability todeliver a system solution for a connected device, such as a connectedthermostat, which would keep itself connected to a cloud network, whichwould have a nearly instant response to any user actions (via Cloud orMobile App), and which would not need a too-often periodical powersource (e.g., battery) replacement, could achieve a large market shareamongst the connected devices actually sold. Moreover, the price of sucha device may also play a major role in the overall connected devicemarket share (i.e., the hardware and software solution must be cheap andcompetitive).

In certain embodiments discussed herein, a low-power long-life (BatteryPowered) cloud connected device (e.g., a thermostat) enabled by aNarrowBand Internet of Things (NB-IOT)/low-powered wide area network(LPWAN) may be disclosed. Examples of this device may be one possibleapproach to the task described. In some examples, the device maydescribe a system solution, which consists of a connected thermostat,designed to run as a low-power system, utilizing the NB-IOT/Lora/(andalike) connectivity type (e.g., the LPWAN connectivity) in a wayapplicable to the Honeywell Connected Edge Devices (e.g., ConnectedThermostats). Through a specific selection of such a connectivitymechanism, multiple issues previously present in all the connectedthermostat offerings may be removed. Furthermore, the overall end-to-endsystem design may be described by examples discussed herein.

Some examples discussed herein, may cover a generic or a specificapproach of providing a direct link connection between connected devicehardware, and a Local Service Provider (e.g., a local public radionetwork manager, such as Verizon (US), CRA (CZ), or the like). Thisconnection might be done through a generic LTE link; yet these examplesmay cover a specific, previously unmapped area, in order to achieve thepreviously listed goal of a direct LPWAN connection between theconnected device hardware, and the Cloud and Mobile App part, as acomplete end-to-end system. Embodiments of the present disclosure mayexpand the end-to-end system design of a cloud-connected thermostat (orany such device) ecosystem, by providing a fully-alternate solution, notexisting on market as of today. For instance, there are manycloud-connected devices that are connected using various technologies,such as Wi-Fi, Sub-GHz and such. Currently, each device needs a local“gateway” which needs to be installed and maintained by thehomeowner/user, including a periodical payment by the homeowner/user tothe Internet Service Provider, in order to retain a connectivity to sucha gateway (e.g., Wi-Fi router, Sub-GHz gateway, and so forth).

According to various embodiments, a device may be disclosed that doesnot need a local, Service provided, connectivity. In some examples, asolution may be proposed that removes a need for any locally owned andmaintained hardware. The idea of a having a direct link from a device toa cloud, while removing the homeowner/user and an “ISP-last-mile” fromthe connectivity path, is new in the area of smart devices, for example,smart thermostats.

In some examples, the connected device may be directly connected to anLPWAN Service Provider, through a worldwide standardized protocol (e.g.,NB-IOT, Lora, or other protocol). This may allow a company such asHoneywell to design a single product, which could be easily provisionedto connect to any such regional network (either by the company, based onthe area-of-sale, or by a contractor who would install such a device).The provisioning system may be simple enough that a homeowner/user maybe able to do this on its own.

In some examples, the device disclosed may remove a complete HUE problemof the Home-Owner-driven installation of the connectivity part of aproduct. This may alleviate struggles, on the Home-Owner's part, wherethis generated a lot of Customer Care calls. In some cases, examples maydescribe a direct LPWAN connection provided for a connected device,while removing all the intermediate steps (Internet “last-mile”) as itwas known before (Wi-Fi connectivity), which cause a wide area ofproblems (Wi-Fi router incompatibility, for example). In some examples,the LPWAN connection may be so low-power, that it enables the connecteddevice to stay connected (through a LPWAN's cloud to a company cloud)and it runs over a world-wide standardized protocols and widely deployedLPWAN networks, while being able to run from a small set of powersources (e.g., batteries) over a period of multiple years, beforeneeding a replacement.

In some cases, the cost of an LPWAN connected device may dropsignificantly, compared to a device connected via Wi-Fi (as oneexample). This may allow a competitive edge in the market place. In someexamples, the LPWAN connected hardware may be so low powered, that italso decreases the temperature impact on the device; which is anotherissue that requires a special approach on the related art devices (i.e.,a need for a “thermal compensation” for a Wi-Fi connected device, wherethe connectivity (Wi-Fi) part adds significant heat to the device body,thus requiring an elaborate and fragile system to compensate thephysically measured temperature to a true in-room temperature value).Furthermore, in various embodiments, the connectivity may be maintainedcompletely out of any failure mode, the Home Owner, or the ISP with itslast-mile connection. This is a frequent issue for the prior connecteddevices, where the Wi-Fi and Internet connectivity is causing a lot ofissues and unhappy customers.

In certain embodiments, a simplified commissioning (installation)process for a connected device, may be described. In some cases, aSystem Design, focusing on three major areas: the Edge Device part(i.e., the connected device), the Cloud System Design, and finally theremote device part of the system. In some examples, the connected devicemay consists of a device core (e.g., a control algorithm, a userinterface, a temperature measurement, or so on), a remote connectivitypart (e.g., an LPWAN connection, utilizing a LoRa, NB-IOT or similarradio-link very-low-power interface) to provide a link between thedevice itself and the cloud, and a local connectivity part (e.g.,Bluetooth Low Energy, for example) to provide a possibility for aphysically-local configuration process (using a smartphone to set upvarious parameters of a connected device).

In some cases, the device core may be a default, re-usable core,tailored to specific product needs. In some cases, the remoteconnectivity part may be one of the main areas of this disclosure. Forinstance, the use of LPWAN connectivity may dictate a small, binaryprotocol to be used. For example, a typical size of a message may beabout 10 to 100 bytes. This is one of the primary drivers to allow for alow power, long-life connected device. The remote connectivity may beconstantly available, as it keeps itself in an ultra-low-powerconsumption state, until a message is to be received or sent. In someexamples, the round-trip-time for a message (send by a Home-Ownerthrough Cloud to a device) may be less than a few seconds, typicallyabout a second, when sent utilizing a LPWAN network. In certainembodiments, the local connectivity part may be used to both commissiona device, and for any local device control by a Home-Owner (utilizingHome-Owner's mobile phone with a Honeywell or other company App). Bycombing a remote and local connectivity, the Home-Owner user'sexperience may be very positive. At home, this provided almostinstantaneous response on any action taken by the Home-Owner (change onApp instantly reflects on Device, and vice versa), while the remotecontrol and monitoring may also be quick and pleasant (within seconds oneach change).

According to various embodiments, the rate on which the LPWAN isutilized to send messages may be configurable. For instance, during apeak moment (e.g., schedule change, remote temperature changes,geofence, or the like) there could be multiple messages sent while therest of a day, there might none or very few to none messages sent.

In some cases, the commissioning part may be required to properly allowa connected device to join a regional LPWAN network. For instance, on aLoRa based network, a few inputs may need to be provided (e.g., networkID, keys, or so on) which could be provided by the factory in advance;transferred to the connected device via the local-link (e.g., aBLE-link) from a remote device (e.g., a mobile phone with theapplication) during installation (or reinstallation) in a building.

Each part may be designed in a way that makes a user, operator,technician, or Home-Owner completely free of any bother on that partbecause the mobile-phone application can do this transparently (whilethe Contractor or the Home-Owner proceeds with the initial setup of theparameters, such as a heating equipment type, the App that would be usedfor that part, will also transfer the LPWAN-provisioning data to thephysical device, based on the inputs from the factory and possiblylocation data to pick the right LPWAN network, and so forth). Thefactory may then have control over the device even before the userdecides to finally configure it. Typically, the factory may create aunique identifier (e.g., a MACID) to each manufactured device. ThisMACID may stay with the device through its whole existence, and itexists in parallel with the LPWAN network identifier. The actualassignment between the physical device (represented by the MACID), theLPWAN-identifier, and the actual user (i.e., the user's account), willhappen once the mobile app connects to the very device (e.g., once appdoes all the above-mentioned background data-transfers to the device).It is possible for the factory to not only assign the MACID on themoment of manufacture, but also to assign a specific LPWAN-identificator(e.g., all the required data and keys to identify a device to LPWAN)during the same moment of manufacture. This may be possible in casethere is an agreement between the factory and the LPWAN networkproviders.

In some cases, the cloud solution may consist of a two parts, aCloud-to-Cloud (C2C) part which may connect each regional LPWAN networkprovider's cloud system, to a company such as a global Honeywell cloud(e.g., Granite Global Integration Layer). This is an industrial standardof doing LPWAN. A remote device may then only need a direct Honeywell orother company Cloud connection (via any Internet link—be it LTE, Wi-Fi),and a local BLE link to control the connected device once in itsvicinity. While the BLE link is utilized, the remote device has theHoneywell or other company Cloud Connectivity available as well. In thiscase, the remote device may not be connected directly to the LPWAN asthere is an alternate Cloud link.

Turning now to the figures, FIG. 1 is a schematic block diagram of anillustrative building control device 100. In the example shown, thebuilding control device 100 includes a controller 102 (e.g.,microcontroller, microprocessor, or the like) operatively coupled to amemory 104, a transmitter 106 (sometimes a transceiver), a sensor(s) 108(e.g., temperature sensors, humidity sensors, other environmentalsensors, occupancy sensors, light sensors, current sensors, smokesensors, or so on), a communication module 110, and a power source 140.The memory 104 and/or sensor(s) 108 may be located in a housing 112 ofthe building control device 100 and/or located remotely from thebuilding control device 100.

The transmitter 106 may be configured to communicate using one or morewireless communication protocols, such as cellular communication,ZigBee, REDLINK™, Bluetooth, Wi-Fi, IrDA, infra-red (IR), dedicatedshort range communication (DSRC), EnOcean, radio frequency (RF) signalsand/or any other suitable common or proprietary wireless protocol, asdesired. In some cases, the transmitter 106 may communicate commandsfrom the building control device 100 to a remotely located buildingcontrol component 114 (e.g., HVAC unit, security unit, lighting unit,fire unit, access control unit, or so on). In certain embodiments, thebuilding control component 114 or an onboard controller of the buildingcontrol component 114 may include a receiver, and the transmitter 106may transmit control commands to the building control component 114,which are then carried out by the building control component 114. Forexample, in certain embodiments, the transmitter 106 of the buildingcontrol device 100 may communicate commands with an HVAC unit using anysuitable communication protocol, such as the BACnet protocol. In somecases, the transmitter 106 may communicate with a security unit usingany suitable communication protocol, such as the DC-09 protocol. In somecases, the transmitter 106 may communicate with a fire unit using anysuitable communication protocol, such as the Modbus protocol. In somecases, the transmitter 106 may communicate with an access control unitusing any suitable communication protocol, such as the EnOcean protocol.In some cases, the transmitter 106 may communicate with a lighting unitusing any suitable communication protocol, such as the DALI protocol.These are just examples of building control network protocols that maybe used to facilitate communication between the building control device100 and discrete building control components (e.g., the building controlcomponent 114). Other building control communication protocols mayinclude, 1-Wire, C-Bus, CC-Link Industrial Networks, DSI, Dynet, KNX,LonTalk, oBIX, VSCP, xAP, X10, Z-Wave, INSTEON, TCIP, Ethernet, and/orany other suitable communication scheme. It is contemplated that thecommunication may be uni-directional or bi-directional, as desired.

In some cases, the building control component 114 may include its ownsensors (e.g., temperature sensors, humidity sensors, otherenvironmental sensors, occupancy sensors, light sensors, currentsensors, smoke sensors, or so on). The building control component 114may be configured to monitor and control the settings and conditions ina space based on the sensed parameters sensed by its own sensors.

In some instances, the controller 102 of the building control device 100may include a pre-programmed chip, such as a very-large-scaleintegration (VLSI) chip and/or an application specific integratedcircuit (ASIC). In such embodiments, the chip may be pre-programmed withcontrol logic in order to control the operation of the building controldevice 100. In some cases, the pre-programmed chip may implement a statemachine that performs the desired functions. By using a pre-programmedchip, the controller 102 may use less power than other programmablecircuits (e.g., general purpose programmable microprocessors) whilestill being able to maintain basic functionality. In other instances,the controller 102 may include a programmable microprocessor. Such aprogrammable microprocessor may allow a user to modify the control logicof the building control device 100 even after it is installed in thefield (e.g., firmware update), which may allow for greater flexibilityof the building control device 100 in the field over using apre-programmed ASIC.

According to various embodiments, the communication module 110 of thebuilding control device 100 may permit the building control device 100to communicate over one or more low power wireless networks, such as lowpower network 118, for example. In some instances, the low power networkmay operate as a “gateway” that allows the building control device 100to communicate over one or more wireless networks, such as network 120.In some cases, the low power network 118 may be a low power wide areanetwork (LPWAN) and the communication module 110 may utilize a wirelessprotocol to communicate over the LPWAN. Examples of the low powernetwork 118 may include, but are not limited to, a LoRa, Sigfox,Telensa, NarrowB and Internet of Things (NB-IOT), Nwave, Weightless,DASH7, LTE, and MySensors. In some cases, the communication module 110may allow the building control device 100 to communicate with a remotedevice 116 over networks 118 and 120. In some cases, network 120 mayinclude a Local Area Networks (LAN) such as a Wi-Fi network and/or aWide Area Networks (WAN) such as the Internet and/or a cellular network.These are just some examples.

In various embodiments, the memory 104 of the building control device100 may be operatively coupled to the controller 102 and may be used tostore any desired information, such as application programs (e.g.,connection application 126), network credentials, setpoints, IR codes,an IR database, schedule times, zones and groupings of building controlcomponents (e.g., building control component 114), and the like. Thememory 104 may be any suitable type of storage device including, but notlimited to, RAM, ROM, EPROM, flash memory (e.g., NAND flash memory), anexternal SPI flash memory, a hard drive, and/or the like. In some cases,the memory 104 may include two or more types of memory. For example, thememory 104 may include a RAM, a ROM and a flash memory module.

During operation, the controller 102 may store information within thememory 104, and may subsequently retrieve the stored information fromthe memory 104. In some cases, program/utility 124 may be stored in thememory 104 and may include a set of application program modules (e.g.software), such as the connection application 126. In some cases, theprogram/utility 124 may include additional program modules as well as anoperating system, one or more other application program modules, and/orprogram data. According to various embodiments, the application programmodules (e.g., the connection application 126) may include networkcredentials, network ID, keys, for example. In certain embodiments, theconnection application 126, including the network credentials, may beassembler instructions, instruction-set-architecture (ISA) instructions,machine instructions, machine dependent instructions, microcode,firmware instructions, state-setting data, or either source code orobject code written in any combination of one or more programminglanguages, including an object oriented programming language such asSmalltalk, C++ or the like, and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages.

The connection application 126 may execute on the building controldevice 100. In some cases, the connection application 126 may execute ona remote device (e.g., remote device 116). In some cases, part of theconnection application 126 may be executed on the building controldevice 100 and part of the connection application 126 may be executed onthe remote device 116. In the latter scenario, the remote device 116 maybe connected to the communication module 110 of the building controldevice 100 through a low power network (e.g., low power network 118) andanother type of network (e.g., network 120). For instance, the low powernetwork 118 may be an LPWAN connected to the network 120 that may be alocal area network (LAN) or a wide area network (WAN), or the low powernetwork 118 may be connected to the remote device 116 via a router (forexample, through the Internet using an Internet Service Provider). Insome cases, the connection application 126 may provide instructions tothe controller 102 to use the communication module 110 to establish adirect low energy wireless connection (e.g., a low energy Wi-Ficonnection, a Bluetooth low energy (BLE) connection, a low energy radioconnection, or other connection) with the remote device 116, bypassing anetwork (e.g., networks 118 and 120), a wireless router, or the like.

The power source 140 may provide power to the building control device100 for its operations. In some examples, the power source 140 may be anon-rechargeable lithium-based battery. In other examples, anon-rechargeable battery may be made from other suitable materials, asdesired. In some instances, the power source 140 may be a rechargeablebattery, which may help increase the useable lifespan of the buildingcontrol device 100. In still other examples, the power source 140 may besome other type of power source, as desired. According to variousembodiments and as stated herein, the communication module 110 may beconfigured to communicate over the low power network 118 and throughdirect low energy wireless connections. This may enable the buildingcontrol device 100 to establish wireless connections covering longdistances with minimum power consumption and maintenance. As such, thepower source 140 may have sufficient battery capacity to power thebuilding control device 100 over a period of years or even decades whilemaintaining a direct link connection between the building control device100 and a Local Service Provider (e.g., network 120) and remote devicesconnected to the network 120 (e.g., the remote device 116).

According to certain embodiments, the remote device 116 may include auser interface 122, an I/O interface 134, a controller 132, a low powernetwork I/O interface 142, and the memory 130 configured similar tomemory 104. In some cases, the user interface 122 may permit the remotedevice 116 to display and/or solicit information, such as desiredenvironmental conditions (e.g., temperature settings, humidity settings,or other settings), security settings, lighting settings, from a user,as well as accept one or more user interactions with the remote device116. Through the user interface 122, the user may, for example, view andmanage the building control device 100 and thus, the building controlcomponent 114. When provided, the ability to view and manage thebuilding control device 100 and/or multiple building control devices mayfacilitate improved management of a building, house, or other structure.In some cases, the remote device 116 may be a smart phone, a tabletcomputer, a laptop computer, a desktop computer and/or any othersuitable device, and the user interface 122 may be a physical userinterface that may include a display 136 and/or a distinct keypad 138.The display 136 may be any suitable display. In some instances, thedisplay 136 may include or may be a liquid crystal display (LCD), anOLED, or other display technology, and in some cases a fixed segmentdisplay, a dot matrix LCD display, a 7-segment type display, and/or mayinclude one or more LEDs. In some cases, the display 136 may include atouch screen LCD panel that functions as both the display 136 and thekeypad 138. In some cases, the user interface 122 may be adapted tosolicit network credentials, but this is not required.

In some instances, the I/O interface 134 may be configured to permit theremote device 116 to communicate over network 120. In some cases, the1/O interface 134 may be configured to communicate with two or morecontrollers, including the building control device 100, for example.

In some instances, the low power I/O interface 142 may be configured topermit the remote device 116 to communicate over the low power network118 and establish a direct low energy wireless connection. In somecases, the low power 1/O interface 142 may be configured to communicatewith two or more controllers, including the building control device 100,for example, over the low power network 118 and/or through a localdirect low energy wireless connection.

As shown in FIG. 1, the remote device 116 may also include thecontroller 132 configured similar to the controller 102 of the buildingcontrol device 100, and memory 130 configured similar to memory 104. Asdiscussed herein, in regard to the controller 102 and memory 104, memory130 of the remote device 116 may be operatively coupled to thecontroller 132 and may be used to store any desired information. Duringoperation, the controller 132 may store information within memory 130,and may retrieve the stored information from memory 130. In some cases,program/utility 124 may be stored in memory 130 and may include a set ofapplication program modules (e.g., app), such as the connectionapplication 126. According to various embodiments, the applicationprogram modules (e.g., the connection application 126) may include orreference network credentials, for example. The connection application126 may be executed on the remote device 116 or part of the connectionapplication 126 may be executed on the remote device 116.

According to various embodiments, the connection application 126 mayenable the building control device 100 to establish multiple connectionswith the remote device 116. For example, the connection application 126may cause the controller 102 of the building control device to monitorthe area for a low power network (e.g., low power network 118) and usethe network credentials (provided by the connection application 126 fromthe memory 104 or from the memory 130, or other storage) toautomatically connect the communication module 110 to the low powernetwork without any assistance from a user, operator, or homeowner. Insome cases, this may be done at installation time of the buildingcontrol device 100. In some cases, the low power network 118 may beconnected to a WAN (e.g., network 120) and the I/O interface 134 of theremote device 116 may be connected to the network 120. As such, theremote device 116 may use the low power network 118 and the network 120to communicate and/or control the building control device 100. Invarious embodiments, the low power I/O interface 142 of the remotedevice 116 may be directly connected to the low power network 118. Inthis case, the remote device 116 may only use the low power network 118to communicate and/or control the building control device 100. Infurther embodiments, the remote device 116 may be in the vicinity of thebuilding control device 100 such that a local low energy direct link(e.g., a BLE link) may be established between the communication module110 and the low power I/O interface 142. In this case, the remote device116 may use the local low energy direct link to communicate and/orcontrol the building control device 100.

FIG. 2 is a perspective view of an illustrative building control device200 that may be an example of the building control device 100 of FIG. 1.In some cases, the building control device 200 may be configured tocommunicate over a low power network and/or through local low energydirect wireless connections. In some examples, the building controldevice 200 may be a thermostat that sends commands (e.g., wirelesssignals) to set, for example, programmable setpoints, operating modechanges and/or other parameters to an HVAC unit. In the example shown,the building control device 200 may include a housing 202 and anoptional stand 204 or other standing feature to aid in placing thebuilding control device 200 on a surface, such as on the surface of atable, desk, counter, or the like. Additionally and/or alternatively, insome cases, the building control device 200 may have a mounting featureto aid in mounting the building control device 200 to a wall or ceilingof a room in a building, house, or structure. If battery powered, thehousing 202 may include a battery compartment for holding a battery orbattery pack (not explicitly shown). The housing 202 may have any shapeor size suitable for housing the internal electronics of the buildingcontrol device 200.

The building control device 200 may include a user interface 206. Insome cases, the user interface 206 may include a display 208. In somecases, the display 208 may include or may be an LCD, an OLED, or otherdisplay technology, and in some cases a fixed segment display, a dotmatrix LCD display, a 7-segment type display, and/or may include one ormore LEDs. In the example shown, the display 208 is a touch screen LCDpanel that functions as both the display 208 and a keypad. In othercases, the user interface may have a physically distinct keypad. Inaddition, the housing 202 may include an opening or window 210 to aid incommunicating with an HVAC unit. The opening or window 210 may extend atleast partially around an outer perimeter of the housing 202. In somecases, the window or opening 210 may be located along the top of thebuilding control device 200. In some cases, the window 210 may betransparent or semi-transparent to low energy signals (e.g., BluetoothLow Energy (BLE)), and a low energy transmitter and/or receiver may bepositioned just behind the window 210. The housing 202 may include alarger opening or window 210 than shown, or multiple windows 210, ifdesired.

FIG. 3A is an illustrative view of an approach 300 for connecting amobile device 306 to the building control device 200. In some cases, themobile device 306 may be connected to network 304. Network 304 may be aLocal Area Networks (LAN) such as a Wi-Fi network and/or a Wide AreaNetworks (WAN) such as the Internet and/or a cellular network, forexample. In some cases, network 304 may be connected to a low powernetwork 302. In some cases, the low power network 302 may be a low powerwide area network (LPWAN). Examples of the low power network 302 mayinclude, but are not limited to, a LoRa, Sigfox, Telensa, NarrowBandInternet of Things (NB-IOT), Nwave, Weightless, DASH7, LTE, andMySensors. During installation of the building control device 200, thebuilding control device 200 may be configured to monitor the area forthe low power network 302. Once the building control device 200discovers the low power network 302, the building control device 200 maythen access network credentials to automatically connect to the lowpower network 302 without any assistance from a user, operator, orhomeowner. Since the building control device 200 is now connected to thelow power network 302, the low power network 302 is connected to thenetwork 304, and network 304 is connected to the mobile device 306, thebuilding control device 200 is connected to the mobile device 306.Accordingly, the mobile device 306 may use the low energy network 302and network 304 to communicate and/or control the building controldevice 200.

According to various embodiments, since the building control device 200is configured to communicate over the low power network 302, thebuilding control device 200 may establish wireless connections coveringlong distances with minimum power consumption and maintenance. As such,the building control device 200 may have a power source that may havesufficient battery capacity to power the building control device 200over a period of years or even decades while maintaining a direct linkconnection between the building control device 200 and network 304.

FIG. 3B is an illustrative view of another approach 308 for connectingthe mobile device 306 to the building control device 200. In some cases,the mobile device 306 may be connected to the low power network 302.During installation of the building control device 200, the buildingcontrol device 200 may once again monitor the area for the low powernetwork 302. Once the building control device 200 discovers the lowpower network 302, the building control device 200 may then accessnetwork credentials to automatically connect to the low power network302 without any assistance from a user, operator, or homeowner. Sincethe building control device 200 is now connected to the low powernetwork 302 and the low power network 302 is connected to the mobiledevice 306, the building control device 200 is connected to the mobiledevice 306. Accordingly, the mobile device 306 may use the low energynetwork 302 to communicate and/or control the building control device200.

FIG. 3C is an illustrative view of another approach 310 for connectingthe mobile device 306 to the building control device 200. In thisexample, the mobile device 306 may be in the vicinity of the buildingcontrol device 200. As such, the mobile device 306 may establish a locallow energy direct link (e.g., a low energy Wi-Fi connection, a Bluetoothlow energy (BLE) connection, a low energy radio connection, or otherconnection) with the building control device 200, bypassing a network(e.g., networks 302 and 304), a wireless router, or the like.Accordingly, the mobile device 306 may use the local low energy directlink to communicate and/or control the building control device 200.

According to various embodiments, since the building control device 200is configured to communicate over a local low energy direct link, thebuilding control device 200 may have a power source that may havesufficient battery capacity to power the building control device 200over a period of years or even decades while maintaining the local lowenergy direct link connection between the building control device 200and the mobile device 306.

Examples described herein can be machine or computer-implemented atleast in part. Some examples can include a computer-readable medium ormachine-readable medium encoded with instructions operable to configurean electronic device to perform approaches as described in the aboveexamples. An implementation of such approaches can include code, such asmicrocode, assembly language code, a higher-level language code, or thelike. Such code can include computer readable instructions forperforming various approaches. The code may form portions of computerprogram products. Further, in an example, the code can be tangiblystored on one or more volatile, non-transitory, or non-volatile tangiblecomputer-readable media, such as during execution or at other times.Examples of these tangible computer-readable media can include, but arenot limited to, hard disks, removable magnetic or optical disks,magnetic cassettes, memory cards or sticks, random access memories(RAMs), read only memories (ROMs), and the like.

To recap, a device may incorporate electronics incorporating atransmitter configured to wirelessly transmit one or more commands to aremote HVAC unit; a communication module for connecting the device to alow power network; a controller configured to communicate with the HVACunit via the transmitter, and communicate with a remote device over thelow power network via the communication module; and a power sourceoperatively coupled to the electronics and configured to power theelectronics.

The device may be further configured to communicate via the transmitterwith one or more sensors for sensing environmental conditions.

The electronics may further include one or more sensors for sensingenvironmental conditions.

The device may further incorporate a housing with the electronics andpower source disposed therein.

The electronics may further incorporate a user interface including adisplay, where the controller may be configured to display on thedisplay current environmental conditions and desired environmentalconditions specified by a user via the user interface.

The remote device may send instructions over the low power network tothe device to control the HVAC unit.

The low power network may be a low power wide area network (LPWAN).

The LPWAN may be a NarrowB and Internet of Things (NB-IoT) Network.

The LPWAN may be a LoRa Network.

The device may be a thermostat.

A thermostat may incorporate a transmitter configured to wirelesslytransmit one or more commands to a remote HVAC unit; a communicationmodule for connecting the device to a low power network; a controlleroperatively connected to the transmitter and the communication module,and configured to communicate with the HVAC unit via the transmitter,and communicate with a remote device over the low power network via thecommunication module; and a power source operatively coupled to thetransmitter, the communication module, and the controller, andconfigured to power the transmitter, the communication module, and thecontroller.

The thermostat may further incorporate a housing with the transmitter,the communication module, the controller, and the power source disposedtherein.

The thermostat may further incorporate one or more sensors for sensingenvironmental conditions, and a user interface including a display. Thecontroller may be configured to display on the display the environmentalconditions and desired environmental conditions specified by a user viathe user interface.

The thermostat may be further configured to communicate via thetransmitter with one or more sensors for sensing environmentalconditions, and the thermostat may further incorporate a user interfaceincluding a display. The controller may be configured to display on thedisplay the environmental conditions and desired environmentalconditions specified by a user via the user interface.

The low power network may be a NarrowB and Internet of Things (IoT)Network.

The low power network may be a LoRa Network.

A thermostat may incorporate a housing; electronics disposed within thehousing, having a transmitter configured to wirelessly transmit one ormore commands to a remote HVAC unit, a communication module forconnecting the device to a low power wide area network (LPWAN), acontroller configured to communicate with the HVAC unit via thetransmitter, and communicate with a remote device over the LPWAN via thecommunication module, a user interface including a display, where thecontroller may be configured to display on the display environmentalconditions and desired environmental conditions specified by a user viathe user interface; and a power source disposed within the housing,operatively coupled to the electronics, and configured to power theelectronics.

The electronics may further incorporate one or more sensors for sensingenvironmental conditions.

The controller may be further configured to communicate via thetransmitter with one or more sensors for sensing environmentalconditions.

The LPWAN may be a NarrowB and Internet of Things (IoT) Network.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Also, inthe above Description, various features may be grouped together tostreamline the disclosure. This should not be interpreted as intendingthat an unclaimed disclosed feature is essential to any claim. Rather,inventive subject matter may lie in less than all features of aparticular disclosed embodiment. Thus, the following claims are herebyincorporated into the Description as examples or embodiments, with eachclaim standing on its own as a separate embodiment, and it iscontemplated that such embodiments can be combined with each other invarious combinations or permutations.

Any publication or patent document noted herein is hereby incorporatedby reference to the same extent as if each publication or patentdocument was specifically and individually indicated to be incorporatedby reference.

In the present specification, some of the matter may be of ahypothetical or prophetic nature although stated in another manner ortense.

Although the present system and/or approach has been described withrespect to at least one illustrative example, many variations andmodifications will become apparent to those skilled in the art uponreading the specification. It is therefore the intention that theappended claims be interpreted as broadly as possible in view of therelated art to include all such variations and modifications.

What is claimed is:
 1. A device comprising: electronics incorporating: atransmitter configured to wirelessly transmit one or more commands to aremote HVAC unit; a communication module for connecting the device to alow power network; a controller configured to: communicate with the HVACunit via the transmitter; and communicate with a remote device over thelow power network via the communication module; and a power sourceoperatively coupled to the electronics and configured to power theelectronics.
 2. The device of claim 1, further configured to communicatevia the transmitter with one or more sensors for sensing environmentalconditions.
 3. The device of claim 1, the electronics further comprisingone or more sensors for sensing environmental conditions.
 4. The deviceof claim 1, further comprising a housing with the electronics and powersource disposed therein.
 5. The device of claim 1, the electronicsfurther comprise a user interface including a display, wherein thecontroller is configured to display on the display current environmentalconditions and desired environmental conditions specified by a user viathe user interface.
 6. The device of claim 1, wherein the remote devicecan send instructions over the low power network to the device tocontrol the HVAC unit.
 7. The device of claim 1, wherein the low powernetwork is a low power wide area network (LPWAN).
 8. The device of claim7, wherein the LPWAN is a NarrowB and Internet of Things (NB-IoT)Network.
 9. The device of claim 7, wherein the LPWAN is a LoRa Network.10. The device of claim 1, wherein the device is a thermostat.
 11. Athermostat comprising: a transmitter configured to wirelessly transmitone or more commands to a remote HVAC unit; a communication module forconnecting the device to a low power network; a controller operativelyconnected to the transmitter and the communication module and configuredto: communicate with the HVAC unit via the transmitter; and communicatewith a remote device over the low power network via the communicationmodule; and a power source operatively coupled to the transmitter, thecommunication module, and the controller and configured to power thetransmitter, the communication module, and the controller.
 12. Thethermostat of claim 11, further comprising a housing with thetransmitter, the communication module, the controller, and the powersource disposed therein.
 13. The thermostat of claim 12, furthercomprising: one or more sensors for sensing environmental conditions;and a user interface including a display, wherein the controller isconfigured to display on the display the environmental conditions anddesired environmental conditions specified by a user via the userinterface.
 14. The thermostat of claim 12, further configured tocommunicate via the transmitter with one or more sensors for sensingenvironmental conditions and the thermostat further comprises a userinterface including a display, wherein the controller is configured todisplay on the display the environmental conditions and desiredenvironmental conditions specified by a user via the user interface. 15.The thermostat of claim 11, wherein the low power network is a NarrowBand Internet of Things (IoT) Network.
 16. The thermostat of claim 11,wherein the low power network is a LoRa Network.
 17. A thermostatcomprising: a housing; electronics disposed within the housing,including: a transmitter configured to wirelessly transmit one or morecommands to a remote HVAC unit; a communication module for connectingthe device to a low power wide area network (LPWAN); a controllerconfigured to: communicate with the HVAC unit via the transmitter; andcommunicate with a remote device over the LPWAN via the communicationmodule; a user interface including a display, wherein the controller isconfigured to display on the display environmental conditions anddesired environmental conditions specified by a user via the userinterface; and a power source disposed within the housing, operativelycoupled to the electronics, and configured to power the electronics. 18.The thermostat of claim 17, the electronics further comprising one ormore sensors for sensing environmental conditions.
 19. The thermostat ofclaim 17, wherein the controller is further configured to communicatevia the transmitter with one or more sensors for sensing environmentalconditions.
 20. The thermostat of claim 17, wherein the LPWAN is aNarrowB and Internet of Things (IoT) Network.